ci: correct the maturity tier, this repo is beta and was running the alpha bundle - #45
Merged
Merged
Conversation
peterjamesnugent
approved these changes
Aug 17, 2026
Contributor
Author
|
@BHoMBot check ready-to-merge |
|
@sakanni to confirm, the following actions are now queued:
There are 5 requests in the queue ahead of you. |
Contributor
Author
|
@BHoMBot check versioning |
|
@sakanni to confirm, the following actions are now queued:
There are 4 requests in the queue ahead of you. |
|
This repository is not part of the beta package and does not require a versioning check to be performed. |
|
@sakanni to confirm, the following actions are now queued:
|
|
@sakanni to confirm, the following actions are now queued:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repository's
maturitycustom property isbeta, but it carriesci-alpha.yml. This swaps it for the beta bundle so the workflow matches the classification. It is the only repository of the 38 onboarded where the two disagree.This adds checks rather than just renaming a file, so it is worth knowing what starts running. Alpha ran build, copyright compliance, project compliance and serialisation. Beta adds code compliance, dataset compliance, documentation compliance, dataset tests and versioning. The new bundle also points at
BHoM/CI_Toolkitand carries the current patterns, so no separate refresh is needed here.Everything stays non-blocking, so nothing here can stop a merge.
Two honest warnings, because these checks have never run on this repository and a first run is where surprises live:
Any compliance finding they report is pre-existing rather than introduced by this change. They were simply not running before.
ci-versioningin particular can misreport on a repository whose subject assemblies do not resolve, attributing other repositories' findings to your pull request. That is a known defect, tracked as CI_Toolkit#200. If you see a large number of findings in namespaces that are not this repository's, that is what you are looking at, and it is not something to fix here.If the beta classification is wrong and this repo should be alpha, say so and I will correct the property instead of the workflow.
Tracked in CI_Toolkit_Proxy#13.